Configure AdminConsole on TomEE

  • Create a directory on the TomEE server to store various configuration files for OIPA (i.e., /%Tomee_Home%/shared or C:\tomee\shared).

  • Create subdirectories inside the directory from Step 1 called conf and lib.

  • Copy AdminConsole-tomEE.war file from the AdminConsole distribution zip file into the webapps subdirectory of TomEE server (Ex : /%Tomee_Home%/webapps or D:\tomee\webapps).

  • Rename the war to AdminConsole.war.

  • Copy the following configuration files from AdminConsole-tomEE-distribution.zip/conf directory into the \shared\conf directory under TomEE server:

    • ac.properties

    • ac-oipa-jmxconnection-content.xml

  • Copy the following files from the OIPA distribution zip/libs directory into the shared\lib directory:

    • jakarta.persistence-api-4.0.0-M1.jar

  • Copy the database drivers for your database into lib directory of TomEE (%TomEE_Home%/lib folder)

    • Oracle – The necessary driver, ojdbc17-23.6.0.24.10.jar, is included in the libs directory of the OIPA Media Pack.

      Note: Version 12.2.0.0 is also supported on Oracle 19c, which is LTS (Long Term Support) and Oracle 26ai. If Oracle 19c or Oracle26ai are used, the corresponding supported ojdbc driver version shipped with Oracle database should be used in the step above.

    • Microsoft SQL Server-Use the compatible jdbc driver shipped with MS SQL Server software. These files are not available for download. Contact your IT department if you need assistance locating these files.

    • IBM DB2 – Use the compatible jdbc driver shipped with DB2 software. These files are not available for download. Contact your IT department if you need assistance locating these files.

  • Use a text editor to open the ac.properties file that was copied to the server. The ac.properties file contains properties for Oracle, SQL Server, and DB2 database types, with the Oracle settings active by default. The inactive settings are commented out with a # character at the start of each line. To change a setting, remove the # from the required property setting, and insert it at the beginning of the preferred setting to de-activate.

  • The properties setting must match the type of database being used:

    • application.databaseType

    • jpa.databasePlatform

      Note: Refer to the System Properties document in the Oracle Insurance Policy Administration E91417_01 Documentation Library on the OTN for a complete list of all properties and allowed values.

  • Use a text editor to open the logging.properties file copied to the server.

  • Edit the path mentioned for property "java.util.logging.FileHandler.pattern" with the new application log location i.e. if the application log location is /home/AdminConsole/logs then set this value as java.util.logging.FileHandler.pattern = %h/AdminConsole/logs/servicelayer%u.log. Make sure that the directory is created and has r/w permission.

    • Set Environment Variables - TomEE

    Trust store password cycle.trustStorePassword, service.trustStorePassword are are now moved to environment variables. These passwords should be added in setenv.bat file in windows, setenv.sh file in Linux

    For Windows deployment we need to create setenv.bat file in the bin folder of extracted TomEE directory.

    set cycle.trustStorePassword=<cycle trust store password>
    set service.trustStorePassword = <service trust store password>

    For Linux deployment we need to create setenv.sh file in the bin folder of extracted TomEE directory.

    Note: Each argument should be separated by space and not the next line(Enter)

    For Linux environment in setenv.sh

    export cycle.trustStorePassword=<cycle trust store password>
    export service.trustStorePassword = <service trust store password>

    Creating Data Sources

    tomee.xml is the file where all the data sources and JMS configurations are done. Any data source, which is needed by an application to run, has to be configured in this file. AdminConsole requires ADMINCONSOLEDS data source to be created.

    Sample configuration of all the data sources which are required for AdminConsole to run:

    Sample Configuration of Data Sources:

    <Resource id="ADMINCONSOLEDS" type="javax.sql.DataSource">

    jdbcDriver = oracle.jdbc.driver.OracleDriver

    jdbcUrl = jdbc:oracle:thin:@localhost:1521:orcl

    userName = <User>

    password = <Pwd>

    jtaManaged = false

    </Resource>

    Configuring Ports

    The server.xml should be configured with unique port numbers in the Server.xml

    <Connector port="8084" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8803" maxParameterCount="1000" xpoweredBy="false" server="Apache TomEE" />

    Deploying AdminConsole

    1. Rename the AdminConsole war, which is generated using AC-tomEE profile, from the distribution to AdminConsole.war.
    2. Deploy AdminConsole war in webapps folder of TomEE application server.
    3. Finally start the server and test the deployment with the url: http://hostname:port/AdminConsole

    Note: If the context name is changed, use that name in the URL instead of AdminConsole.